| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
   |
Posted - 2012.04.13 18:07:00 -
[1] - Quote
Adding my name to the list. Australia too.
Happened twice tonight and has been happening over the past week or so.
Did this traceroute about 40 mins after the second crash so not sure if it will help but in any case.
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms bob.iad [10.1.1.1]
2 18 ms 18 ms 19 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 18 ms 19 ms 21 ms te7-2.per-qv1-bdr2.iinet.net.au [203.215.4.38]
4 66 ms 68 ms 66 ms po1-100.per-qv1-bdr1.iinet.net.au [203.215.20.13
0]
5 66 ms 67 ms 66 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
6 70 ms 71 ms 71 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.1
37]
7 70 ms 71 ms 70 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
8 66 ms 68 ms 68 ms te6-1-100.mel-pipe-bdr2.iinet.net.au [203.215.20
.139]
9 73 ms 77 ms 73 ms xe-0-1-0-0.syd-mas-core1.iinet.net.au [203.215.2
0.106]
10 156 ms 72 ms 71 ms ae0.syd-ult-core1.iinet.net.au [203.215.20.110]
11 72 ms 71 ms 71 ms 26629.siko06.cu.reach.com [134.159.126.45]
12 75 ms 76 ms 74 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1
]
13 214 ms 212 ms 211 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.1
46]
14 278 ms 405 ms 411 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
15 243 ms 244 ms 243 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
16 405 ms 295 ms 295 ms 204.245.39.42
17 304 ms 301 ms 303 ms srv245-e.ccp.cc [87.237.36.245]
18 303 ms 302 ms 303 ms srv248-e.ccp.cc [87.237.36.248]
19 297 ms 297 ms 300 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete. |
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
|
Posted - 2012.04.14 13:13:00 -
[2] - Quote
Still dropping out today.
After first drop out I ran with ping -t going.
This is what it was like on second drop out.
Reply from 87.237.38.200: bytes=32 time=296ms TTL=116
Reply from 87.237.38.200: bytes=32 time=299ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
During this time I could not contact eveonline.com however was still connecting to other websites fine.
And again.
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
Reply from 87.237.38.200: bytes=32 time=298ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=298ms TTL=116
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
This time I lagged but it did not crash the client.
|
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
|
Posted - 2012.04.22 16:17:00 -
[3] - Quote
Still happening to me, not as often though. |
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
|
Posted - 2012.04.24 12:15:00 -
[4] - Quote
Also with regards to it been an Australian problem, why is it only EVE, and EVE sites becoming unresponsive, while the rest of the interwebs works fine. Also a number of people from other countries like Ueberlisk have said they are having the same/similar issue.
ItGÇÖs not like our ISP's are failing, as the internet is still functioning it something specific. But knowing a very little bit about how the internets works, this type of problem is really bull **** hard to troubleshoot.
However I would really like CCP to say something else on the matter, itGÇÖs been over a week. Just so we know we are not talking to a brick wall.
|
Leads Dent
Dark Fusion Industries
Limitless Inc.
2
|
Posted - 2012.04.28 18:19:00 -
[5] - Quote
Glijaron wrote:Still no discos and running solid... Thank you CCP! I'll call it fixed ! 
Humour me, can you post your traceroute info please. |
Leads Dent
Dark Fusion Industries
Limitless Inc.
2
|
Posted - 2012.05.02 03:31:00 -
[6] - Quote
It seems like the only way to get a responce from CCP is to make a petition. So if your not in this blanked excuse that is it an Australian and New Zealand problem I suggest you make a petition.
It is unfortunate but if it is reach.com as a backbone provider causing the problems there is not really anything that can be done about it. CCP has no way of making them provide better service because they do not provide any direct service to CCP and same for the ISP's. It is probably worth checking if you not is Aus, NZ that if you still sending traffic through the Reach backbone, there is talk about which IP that is somewhere on page 9 I think. If your not using Reach I suggest you take your problem to another topic as I think this one has been labelled the Reach specific problem.
However the internet is a dynamic thing so if the game is unplayable now, come back in a month or something and it could be all better. Saying that I have been very lucky the last couple of days as it *seems* to be pretty stable, only the odd d/c ever second day.
It still really sucks that CCP said they are looking into this. Then felt that we deserved no more feedback, even if it is just. "sorry guys, not our fault, blame these peoples"
Pisses me off to be honest. |
| |
|